home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The 640 MEG Shareware Studio 2
/
The 640 Meg Shareware Studio CD-ROM Volume II (Data Express)(1993).ISO
/
bbs
/
lcnt150u.zip
/
LOGCOUNT.CFG
< prev
next >
Wrap
Text File
|
1992-11-27
|
38KB
|
736 lines
%
% --------------------------------------------------------------------------
% --------------------------------------------------------------------------
% NOTE: This sample file contains lots of information that is purely
% descriptive and commentary. the actual .CFG file need only
% contain the runtime parameters. This will speed up processing
% if LOGCOUNT does not have to ignore all the non commands.
% Parameters can be placed in any order and are case insensitive.
%
% ALSO NOTE: This program uses the default characters '[' and ']' to
% contain the download information. If you have been using
% another utility which uses '(' and ')' then investigate
% the -X and -Y options, if you run the program without
% proper configuration, your FILES.BBS will be altered and
% the descriptions will be truncated. Be Careful.
%
%
%
% --------------------------------------------------------------------------
% --------------------------------------------------------------------------
%
% LOGCOUNT.CFG Format, all command line options start with '-' or '/',
% all other lines are ignored. Commands in the .CFG file are exactly
% the same as command line options, NO SPACES are permitted between
% the identifier and the parameter. The first 'word' on the line must
% be the 'identifier/parameter' and any other 'words' will be ignored.
% You can put comments of the same line as your command line options.
% Just make sure that at least TWO space character separates the command
% line parameter from the description. LOGCOUNT will look for LOGCOUNT.CFG
% in the executing directory if no command line -C<config.CFG> has been
% specified. It will use any parameters found in it, any other command
% line options will override what is in the .CFG file.
%
% When LOGCOUNT is processing a FILES.BBS file, any blank lines, lines
% that begin with a space (ascii 32) of a hyphen '-' or a '@' symbol
% will be considered a 'comment' line, and will be ignored, any other
% character as the first character of a line will be treated as a
% filename. If no inclusion is contained in the line, then one will
% be added, don't put comments starting at the first character of the
% line, CBCSystems don't like it, and neither will LOGCOUNT.
%
%
%
%
%----------------------------------------------------------------------------
%
%
% -L Parameter -=> CBCS Log file to be read. A Maximus/Opus .LOG File
% or a QBBS system log file.
%
% full drive/path/filename is optional, if no path is
% given then the current directory will be searched for
% file.
%
% --------------------------------------------------------------------------
%
% -B Parameter -=> BinkleyTerm format Logfile. (drive/path optional).
%
% --------------------------------------------------------------------------
%
% -F Parameter -=> FrontDoor/RA format Logfile. (drive/path optional).
%
%
% Note: Since these two 'different' format files use the same parameter
% the last run information may not always be valid. If you run
% Logcount on two different log files in the same directory, then
% the last run information will certainly not be valid. Try moving
% either your FD or RA logfile to another directory before running
% LOGCOUNT on your second logfile.
%
% --------------------------------------------------------------------------
%
% -D Parameter -=> history Download file. (if you specify a -D option
% in the .CFG file and then specify a '-D' parameter
% with no filename then this will turn off the download
% history file option. If used with -B option then all
% files 'sent' will be logged, Netmail etc.. will not
% be logged.
%
% --------------------------------------------------------------------------
%
% -U Parameter -=> history upload file. (if you specify a '-U<filespec>'
% parameter in the .CFG file and then specify a '-U'
% parameter with no filename then this will turn off
% the uploads history file option. If used with the
% -B or -F options ALL files uploaded (received) will
% be logged.
%
% NOTE: Both the -D<log_file> and the -U<up_file> can be pointed
% to the same file, this keeps everything together, I prefer
% to keep one complete history log, but to each his/her own.
% .REQ files will only be logged if both history logs point
% to the same file, otherwise .REQ files are not reported in
% the '-U' upload (request) history file.
%
%
% -J<filename> CBCSlogFile option, filenames that match will update the
% files.bbs if that option is active. These filenames will not
% be entered in any history logfiles. Wildcards '?' can be used,
% doesn't support '*' wildcards. The name will be checked
% character by character. Maximum 25. Simple names only,
% no path info...
%
% eg. -jnodediff.a??
% eg. -jfnews???.arc
% eg. -jMaximus.Qwk
% eg. -jMaximus.Rep
%
% --------------------------------------------------------------------------
%
% -K parameter -=> intructs LOGCOUNT *not* to include the remote system's
% SysOp's name in the history files. Only applicable if
% processing a `-b' Binkleyterm or `-f' FD log file.
%
% this might be needed for a `-f' DB log! DB logfile
% is not very well known by author of LOGCOUNT.
% --------------------------------------------------------------------------
%
% -E parameter -=> This parameter indicates exactly what type of
% 'Time of Transfer' information to include in your
% history log files. The default is to have NONE.
% The date of 'transfer' is always included.
%
% -EH Will only include the Hour of the transfer.
% -EHM will include the Hour and the Minutes,
% -EHMS will include the hour, minutes and seconds.
%
%
% --------------------------------------------------------------------------
%
% -X Parameter -=> custom bracket character for left bracket.
% the default is '-x[' and not '-x(' !!!!!!!!!!
%
% -=> can contain 'invisible' Avatar Colour codes.
% maximus length of 24 characters.
%
% -x[, < -=> enhanced function, normal files use '[', free files
% counts will be enclosed by '<' character.
%
% --------------------------------------------------------------------------
%
% -Y Parameter -=> custom bracket character for right bracket.
% the default is '-y]' and not '-y)' !!!!!!!!!!
%
% -=> can contain 'invisible' Avatar Colour codes.
% maximus length of 24 characters.
%
% -x], > -=> enhanced function, normal files use ']', free files
% counts will be enclosed by '>' character.
%
%
% Note: This is the only way to pass Characters that DOS will
% interpret as Redirection commands. '>', '<', and '|',
% can't be passed from the DOS Command line.
%
% If you change 'bracket' characters, then you will have to use
% a text editor to make GLOBAL changes, the program will not do
% that for you, if you run the program on an existing files.bbs
% that uses a different format from the default or the configured
% setup, things will get real messy ! Filename.ext [ ] (45) description
% will be the result, you have been warned ! FIXFBBS can do this,
% but be sure to backup your FILES.BBS files before experimenting
% with FIXFBBS and AVATAR codes. If you use the enhanced function
% make sure FIXFBBS and LOGCOUNT have been configured with the
% same information. Failure to do this will result in disaster..
%
% --------------------------------------------------------------------------
%
% -R Parameter -=> Identifies what a RECEIVED entry looks like.
% By default this is 'UL-?' for CBCS, 'Rcvd' for FD and
% 'Received-Z/32' for BinkleyTerm. Change this for NoWazoo
% entries. this parameter is case sensitive and must be
% exactly as it appears in the .LOG file.
%
%+ 05 May 00:29:46 BINK Received-Z/32 C:\Opus\Inbound\00000064.sa0
% ^^^^^^^^^^^^^
% example -RReceived-Z/32
%
% SPECIAL NOTE: in order for this option to work correctly you must
% have your logfile options specified in the .cfg file
% *before* this option. Command line overrides for log
% file options also will override this option.
%
% NOTE: Not available as a command line option.
% --------------------------------------------------------------------------
%
% -S Parameter -=> Identifies what a SEND entry looks like.
% By default this is 'DL-?' for CBCS, 'Sent' for FD and
% 'Sent-Z/32' for BinkleyTerm. Change this for NoWazoo
% entries. This parameter is case SENSITIVE and must be
% exactly as it appears in the .LOG file.
%
%+ 05 May 00:28:27 BINK Sent-Z/32 C:\Opus\Outbound\0000ff9c.Fr0
% ^^^^^^^^^
% example -SSent-Z/32
%
%
% Note: The -R and -S options only work if you specify that this is a
% -B or -F format Log file. CBCS log file formats are fixed.
% if you tell LOGCOUNT to expect a BinkleyTerm file it will by
% default start looking for Z-Modem Wazoo information. Of course
% you can specify any file as a Binkley or FD file and use these
% options to search for specific information, the filename will
% be expected to start exactly 2 characters after the parameter
% this allows for one 'space' Character.
%
%
% SPECIAL NOTE: in order for this option to work correctly you must
% have your logfile options specified in the .cfg file
% *before* this option. Command line overrides for log
% file options also will override this option.
%
% EXTRA NOTE: Even though you must specify the whole 'Received' or
% 'Sent' strings, the last character is insignificant, it
% must be there for the correct string size but is ignored
% by the program, this would allow all possible 'DL-?' to
% be recognized in special circumstances. So the program
% is actually looking for 'DL-' and Not 'DL-Z' because
% every protocol has it's own unique identifier.
% BinkleyTerm entries start the line with '+',
% OPUS and Maximus entries start with '=',
% FrontDoor log files start transfer entries with '*'
% Logcount will not identify entries specified as one
% of these known types unless the first character matches.
% The history files maintain the correct identifiers.
%
% NOTE: Not available as a command line option.
% --------------------------------------------------------------------------
%
% -TN Parameter -=> Tells logcount not to truncate lines, this may cause
% wrap around , if your FILES.BBS descriptions are long.
% Lines are truncated by default at 61 Characters, this
% works perfectly with Maximus.
%
% note: this parameter could be configurable if 61 characters is not
% acceptable for all systems. Send me a message.
%
% -TM# Parameter -=> Tells Logcount not to truncate lines, and to adjust
% any long descriptions so they display in an orderly
% manner. Shifting the description part of the second,
% third and fourth lines so that they start under the
% description part of line #1, and not the download
% count. For Maximus v1.02 ++ only. # is set to zero,
% by defauult, specifying a number will alter where the
% justified description will start.
%
% normally Maximus is displaying FileSizes and dates, if Maximus is not
% displaying files sizes and dates, then use '-TM18'. If for any reason
% your descriptions do not align properly, try adjusting the number, -1
% will shift everything one to the right, and 1 would shift everything
% towards the left.
%
% Note: Maximus v2.0x has a Max.Ctl file option to do this adjusting
% by itself. By default (in English.Mad) Maximus expects the size
% of the download counters to be 4 digits in length. FIXFBBS
% relies on the v1.02 formatting of the lines when creating it's
% catalog file. The output may be messy if the v1.02 formatting
% is not found in the files.bbs.
%
%
% -TR# Parameter -=> Tells Logcount not to truncate lines, and to adjust
% any long descriptions so they display in an orderly
% manner. Shifting the description part of the second,
% third and fourth lines so that they start under the
% description part of line #1, and not the download
% count. For Remote Access only. # is set to zero,
% by default, specifying a number will alter where the
% justified description will start.
%
% normally RA is displaying FileSizes and dates, if RA is not
% displaying files sizes and dates, then use '-TR18'. If for any reason
% your descriptions do not align properly, try adjusting the number, -1
% will shift everything one to the right, and 1 would shift everything
% towards the left.
%
% This option no longer seems to work with RA v1.11, I quess it is now
% obsolete. RA v1.11 seems to be recognizing atl #255 characters as
% normal spaces and is killing extra white space when it displays
% long file descriptions.
%
% -#0 is a new option that tells Logcount to insert leading '0's in the
% download counters instead of the normal blank spacing. This will
% fix the problem of RA removing occurrences of double spacing when
% it displays descriptions of more than a single line.
%
% eg.. [0037] instead of [ 37] etc...
%
% RA displays [ 37] as [ 37] if the File description is lengthy.
%
% --------------------------------------------------------------------------
%
% -Q parameter -=> Tells logcount to operate 'Quietly', it will not
% display it's run time options. It will still report
% errors !
%
% --------------------------------------------------------------------------
%
% -H parameter -=> tells logcount to display any runtime options and
% if no .CFG file is found it will display the help
% screen, it will not try to update anything.
%
% --------------------------------------------------------------------------
%
% -H? parameter -=> Will display the help screen, it will not display
% any runtime options like the '-H' parameter.
%
% --------------------------------------------------------------------------
%
% -OR Parameter -=> Not available in the .CFG options, this will cause
% all DOWNLOADS to be added to any existing FILES.BBS in
% the CBCS files areas. In fact if no FILES.BBS can
% be found then one will be created !
% Be carefull using the -OR Orphan command line option.
% This is useful if you ever LOSE your Files.BBS files
% but still have backup log files, and especially if
% you keep the History download log files. They are
% in a similar format as the original CBCS Logs
% and the BinkleyTerm entries have been changed to
% shorten the Wazoo Z-modem entries to 4 character
% abbreviations, using the -R and -S options can read
% these changes ! You can easily recalculate your
% Files.bbs files. This option is OFF by default.
%
% --------------------------------------------------------------------------
%
% -M parameter -=> This tells LOGCOUNT NOT to automatically adjust areas
% <digit 1-7> as the maximum downloaded file amount enters another
% power of ten, but will ALWAYS Maintain this as the
% maximum allowable inclusion. If a file has been
% downloaded 99 times and -M2 has been used then the
% any further downloads will always show 99, the count
% will not increase and the size of the inclusion will
% always remain the same. In fact this parameter will
% force all entries in 'all' of the FILES.BBS files to
% be this same size, regardless of how many downloads are
% the maximum for each different area. This option defeats
% most of the logic involved in the program ! If you have
% been using level '3' and then decide to start using
% level '2' any file downloaded more than 100 times will
% be set at the maximum for the new level, in this case
% 99 would be the maximum with level 2.
%
%
% -M4 would specify '[ ]' values from none to 9999
% -M3 would specify '[ ]' values from none to 999
% -M2 would specify '[ ]' values from none to 99
%
% etc...
% -M7 is the maximum and -M1 is the minimum.
%
%
% By default LOGCOUNT dynamically maintains the inclusions and will adjust
% all entries in an area that has exceeded it's present level, it will
% continue to expand upwards until a maximum limit of [9999999] is reached.
% If a file that was the highest counted download is removed, the next time
% Logcount processes that area if will RECALCULATE the largest download and
% will adjust all entries in that area only. Any new file with only a
% description will also cause a rescan of the area. Filenames with NO
% description will have an 'Orphan File, No description Available' appended
% after a blank download inclusion.
%
% NEW - NEW - NEW - NEW
%
% -m3 C:\UPLOADS - Overrides any 'global' inculsion size in this area
% only. This area is 'fixed' at 3 digits. The characters
% ':\' must be in the directory name. That's the only way
% to distinguish a directory from a comment.
% - Maximum of 15 directories can be listed with this
% override option. Should be plenty.
% - value of the number attached to the letter 'm' can be
% higher or lower than any declared 'global' inclusion
% size.
% -m0 c:\uploads - the 'zero' indicates that logcount should maintain
% this area dynamically. Increasing/decreasing size
% as necessary.
%
% All description files in this directory
% will be included, so be carefull using this kind
% of option if you have multiple descriptions files
% in the same directory. (see the -@ option below).
%
%
%
% --------------------------------------------------------------------------
%
% -Z<extension> -=> This is especially for SDS Distributors and other
% network distributors, This option will accept a 3
% character extension that is often used to attach
% files to other Nodes. If you specify a -Z option
% then the file will be counted as a download, BUT
% when LOGCOUNT recognizes the next file as a special
% extension, it will then decrement the previous entry.
% This will take a little bit longer to do, but will
% result in the files being sent via attaches to other
% system nodes not being counted in your files.bbs
% files. A maximum of 25 such attach identifiers is
% allowed.
% Example: -Ztic
%
% Special Note: If you move files around before your mailer has sent all
% of these special '.Tic' attaches then it is very possible
% that LOGCOUNT will not find them and will attempt to reduce
% the previous file. This is accounted for in BinkleyTerm
% log files, BT will report an error in the log file if is
% supposed to send a file that it can not find. FrontDoor
% does not report this type of error. So if you are using
% FrontDoor and have not sent the file associated with the
% '.Tic', then LOGCOUNT will attempt to reduce the count
% of the previous file downloaded. If the previous file was
% not found in a FILES.BBS or was another '.TIC' or if a
% '.Tic' was the first file sent after a connection to a new
% system then LOGCOUNT will not attempt to reduce a download
% count.
%
% --------------------------------------------------------------------------
%
% -V parameter -=> By default LOGCOUNT will keep track of the last file
% updated, CBCSLAST.BBS or FDRALAST.BBS, or BINKLAST.BBS
% for the various Logs. These files will be maintained in
% same directories as the original LOG files, what LOGCOUNT
% will do is determine if the .LOG file is new or not, if
% the 'time stamp' of the first entry in the file is less
% than the last file updated, then the log file will be
% searched till the point of the file where the last
% successful update occurred and start processing from there.
%
% This option '-V' will turn off this feature and will
% process the entire log, start to finish, be careful or
% your download counts will not be accurate. If you Pack
% or rename your log files, every night after running
% LOGCOUNT, and there is no chance of ever reprocessing
% the log file again, then use this option, It might
% speed up the program a little bit.
%
% --------------------------------------------------------------------------
%
%
% -W<directory> Optional scan of one specified directory, this should
% be your uploads directory, all new files without
% inclusions will have one inserted, just in case no
% downloads have taken place in that area. LOGCOUNT
% will automatically insert a new inclusion in NEW
% file descriptions when it processes the area with
% download information. This option is for inactive
% systems, like mine.
% or
%
% -W<directory/filename.ext> in cases where FILES.BBS is not the
% name of the description file.
% --------------------------------------------------------------------------
%
%
% -A<#> by default the User name will appear starting at
% column 60 in the history log files, if you use
% very LONG path names for your directories, or very
% short names, then you may want to change the position
% where this information is written. No matter what value
% you specify here, a MINIMUM of 3 spaces will be added
% after the filename and before the user name, the reason
% for this is so that that LOGCOUNT can process the
% history files if necessary.
%
% NOTE: If you are using the '-E' options to include 'time of transfer'
% information, then you should be aware that that information
% takes up additional space in the history files, you may have
% to adjust the starting position of the user names if you change
% the amount of 'time of transfer' information. This will make the
% files line up nicely and can easily be sorted.
%
% --------------------------------------------------------------------------
%
% -@ directory_name drive:\path\filename.ext
%
% The intent of this option is to support CDRom but it has other purposes.
% Basically what you do is supply 2 pieces of information. The first being
% the path name that will be found in the logfile being read by LOGCOUNT.
% The second being the full pathname of a file containing the file
% descriptions. Sounds simple enough eh! Not available as COMMAND line
% option, .CFG only. and check your spelling carefully.
%
% for example
%
% -@ C:\max\files c:\descript\filarea.one
%
% anything in a logfile with the exact path of "c:\max\files\" will be
% assumed to have it's description in the file FILEAREA.ONE in
% directory c:\descript.
%
% (if and only if there is not a c:\max\files\FILES.BBS that can be
% succesfully written too!)
%
% this is a direct translation. ( c:\max\files\filename.ext )
%
% -@ C:\max* c:\descrpt\filarea.two
% ^^^^^^
% this is an example of a WILDCARD, if the part to the left of the
% asterick ("C:\Max") can be found in the path in the logfile entry
% then the description of the filename is assumed to be in the
% specified file.
%
% So things like
%
% c:\max\max.exe
% c:\max\files\filename.ext
% c:\max\olr\node01\maximus.qwk
% c:\maximus\files\filename.ext
% c:\max\etc.....
% ^^^^^^
% are all going to have their descriptions in the file
% c:\descrpt\filearea.two
%
% (if and only if there is not a FILES.BBS in the specific
% directory that can be succesfully written too!)
%
%
% finally
%
% -@ * c:\max\files.bbs
%
% Usually this will be your very last "-@' option. The single asterick
% indicates that any file that can not be found in a files.bbs in the
% directory indicated as it's download path, or if all other directory
% translations fail, then this is the last place to look for a description
% for the file. -OR Orphans are sure to show up in here.
%
% The translatable directory stuff need not to be too exact, but the
% filenames with the descriptions must be exact "drive:\path\filename.ext"
% entries. It's a good idea to ensure that these files really exist. The
% usual names for these files is "FILES.BBS" but any legal DOS filename
% is acceptable. These files can contain full drive/path/filenames as well
% as simple filenames and of course the associated descriptions.
%
% Maximum of 75 translatables. (length 63 chars maximum.)
% use wildcard translations....
%
% --------------------------------------------------------------------------
%
% NEW - NEW - NEW - NEW
%
%
% -MaxFiles c:\max ;Maxfiles.Idx, Area.Dat,and Area.Ndx are here!
%
%
% this option allows LOGCOUNT to look up SIMPLE file names in the
% database files compiled with FB.EXE. It will find the simple
% names and find a full path if possible. Specifying MaxFiles tells
% Logcount to lookfor Maxfiles.Idx in the current directory and expects
% to find AREA.NDX and AREA.DAT in the same default directory. If you
% specify Maxfiles with a Path (eg MaxFiles C:\Max) then Logcount will
% look in the specified directory for the Maximus data files.
%
%
% This may be usefull if your mailer does not supply full path
% information with it's file requests. D'Bridge for example.
% You may have to investigate the -r and -s options to get
% Logcount to look for the correct receive and send instructions,
% and have it use the maximus files to determine the path to your
% files.bbs files or FILELIST files in their various directories.
%
% --------------------------------------------------------------------------
%
% -CleanSpace
%
% this option tells logcount not to add extra white space to the
% filenames in the FILELIST (FILES.BBS). Normally all simple names
% are padded to 15 characters, OPUS used to do that and maybe
% Maximus does, not sure. This options disables this function
% only if the files.bbs entry has a path in the filename or has
% any hidden characters (eg. /bt, /b, /t) before the counter.
% Normal simple names are still padded to 15 characters so that
% description fields are more easily detectable by human beings.
%
%
% --------------------------------------------------------------------------
% Advanced features.........
% --------------------------------------------------------------------------
%
%
% -o_Words 2
%
% this tells logcount to expect the download count as the third word
% in the description field. That is there are 2 extra words on the
% line before the download count. if file descriptions include filesize
% or date then the download is not the first thing in the description.
% If Logcount is set for -TM# or -TR# then LOGCOUNT will adjust the
% descriptions so they appear exactly as a normal file listings as
% as they do when maximus is displaying `Automatic Date'. Must be
% either 1 or 2 words maximum. 2 for size and date, etc...
%
% set FILELIST MARGIN 31 in Max.Ctl if description contains size and
% date.
%
% If you set -TN then you'll have to adjust the appropriate variable
% of Maximus to get the descriptions lining up properly. And you'll
% also have set a predetermined maximum counter size limit.
%
%
% -o_Word1 7
%
% This tells LOGCOUNT to format your first word to 7 characters
% oridnary blank space will be added if you have a colour defined
% for the first word, if not then alternate blank, character 255
% will be used. This is usefull if the first word is `filesize',
% a variable length. The word will be right justified in it's field
% The date (o_word2) already has a fixed length format so that word
% needs no adjustment.
%
%
% if we know there are 2 words we can also define the colours we
% want each word to be.
%
% -c_Word1 [magenta] word1 = size..
% -c_Word2 é [green] word2 = date..
%
% don't try to set "-c_word2" if "-o_words" = 1 !
%
% -c_Word3 ä [red]
%
% word3 is optional but usefull, if a filelist has a non numeric
% filesize (1st word) then LOGCOUNT will insert this colour and
% will not treat this as a real filesize and date using the other
% specified colours.
%
% if these advanced features are in use, LOGCOUNT can operate
% on normal files.bbs listing (with only filenames and descriptions)
% and other files with `WORDS' (eg. size and date) as the first
% part of the description at the same time. If a normal description
% has no extra words before the description then LOGCOUNT will not
% attempt to add anything into those words. If there are more words
% found than defined then the whole thing will be considered part of
% the description.
%
%
%
%
% --------------------------------------------------------------------------
% Final feature: Maximus and OPUS allow entries in the FILES.BBS to
% contain Wildcards ! Yes it's true. Maximus is very
% gracious allowing '?' and '*' wildcards. I don't
% know if OPUS allows both wildcard identifiers.
%
% This allows you to place files that have constantly
% changing names if the files areas, the FILES.BBS entry
% would say NODELIST.A?? and the CBCS would display the
% real name of the file, NODELIST.A73. LOGCOUNT only
% understands the use of '?' wildcards, it does not
% understand the '*' and if it ever encounters one it
% will ignore it. There is a perfectly good explanation
% for this. It's much easier to check for '?' wildcards.
% LOGCOUNT will check for these wildcards '?' and will
% update the wildcard FILES.BBS entries.
%
%
% Absolute last feature, option, I really don't like this one !!!!
%
% -NO This turns off the main function of the program,
% updating the files.bbs with the download counts.
% Of course if you disable the updating of the
% FILES.BBS files, then all parameters and functions
% specific to the FILES.BBS will also be disabled.
% I have included this for those of you who wish to
% use the History log file features only. Registered
% users get more features including a comprehensive
% database option, complete system monitoring, including
% special processing of 'Tic' and 'Fle' file attaches.
%
%
% --------------------------------------------------------------------------
% --------------------------------------------------------------------------
% --------------------------------------------------------------------------
%
%
% Example. LOGCOUNT.CFG file.
-ltest.log %CBCS Logfile, starts with -L
%
% -x( %left side 'inclusion' character , default is '['
% -y) %right side " " " ']'
% -m3 %always maintain 3 digit counts.
%
% These above three options may be needed if you have been previously
% using another popular Download counting utility ! The '-M3' option is
% truly optional, but the inclusion characters must match what already
% exist in your FILES.BBS, otherwise all entries will be considered as
% New entries and will given new inclusions. Be Careful, use the -H option.
%
%
-dc:\logs\download.log % history downloads.
-uc:\logs\uploads.log % history uploads.
-wd:\f\uploads\files.bbs % Scan uploads, not very busy around this BBS.
-A50 % Short pathnames, so start user name at column 50
% -TM18 % Maximus 3 line descriptions and NO file info
-TM % 3 Line descriptions, FILESIZE/DATE displayed.
-JMaximus.Qwk % Keep this filename out of history logs.
-JMaximus.Rep % Keep this filename out of history logs.
%
-@ c:\max\olr\node01 c:\max\olr\files.bbs
%
% ( the above option is useful because maximus is continuously creating )
% ( and removing this directory. the -OR option does not create directories )
% ( but using a directory/filename translation allows you to monitor these )
% ( QWK transfers. )
-@ g:* c:\max\files.lst % All files on G: have descripts in files.lst
-@ * c:\max\unknown.lst % last chance description file.
%
%
% These parameters tell logcount to use special 'bracket Characters'
% and that the default log is a CBCS type log file call TEST.LOG If no
% path information is given in the name, it will look for it in the current
% directory, not where LOGCOUNT.EXE is, LOGCOUNT can be anywhere,
% preferably some where on the DOS Path. Seperate Uploads and downloads
% history files will be maintained. LOGCOUNT will keep a CBCSLAST.BBS
% file in the same directory as TEST.LOG, so if the file is updated again
% it will only process newer downloads, and uploads.
%
% If you were now to execute LOGCOUNT -U -D -Bc:\binkley\binkley.log -Ztic
% then the 'blank' history files option would turn OFF the history files
% option. The -B parameter tells LOGCOUNT to ignore the .CFG -L<CBCS> log
% file options and use the default BinkleyTerm Wazoo type entries. The
% special extension of '.TIC' would cause previous files to be 'reduced'
% since their previous increment was due to a file attach, and should not
% be counted as a download.
%
% CopyRight (c) RAFware CBCSystems 1990.
%
% send donations ( $10.00 ), suggestions, or snail mail to
%
% Rodney A. Fraser
% 6429 Halifax Steet,
% Burnaby, B.C.
% V5B 2P7, CANADA.
%
% enclose 5", 360K floppy in self addressed envelope and
% I will send Registered version.
%